Systems and methods for creating software

ABSTRACT

An online software development platform providing an integrated resource for design, development, and purchase of customer-desired software applications for software projects created by customers. The platform comprising one or more computers configured using computer readable instructions stored in non-transitory computer memory to provide the software development platform, wherein the software development platform is configured to implement a plurality of electronic operational domains providing user-interactive capabilities or internal functionalities of the software development platform. The domains comprising a project scope process, a pricing process, and a project development process. The platform is configured to use a configuration involving knowledge graph to recommend features.

CROSS REFERENCE TO RELATED APPLICATIONS

This is a continuation of U.S. patent application Ser. No. 17/348,695,filed Jun. 15, 2021, which claims priority to U.S. Provisional PatentApplication Ser. No. 63/039,968, filed Jun. 16, 2020, the entirety ofeach of which is incorporated herein by reference in its entirety.

FIELD OF THE INVENTION

Embodiments of the present invention are related to the field ofsoftware development. Embodiments of the present invention are relatedto software development platform providing an integrated resource fordesign, development, and purchase of customer-desired softwareapplications for software projects created by customers. Embodiments ofthe present invention are related to software development platformshaving integrated advanced development aspects including machinelearning to incorporate features into applications.

BACKGROUND

The present invention relates to software application developmentsystems and improving the effectiveness, speed, and operation ofsoftware application development. Software development is its own fieldof endeavor and a significant industry exists directed to softwaredevelopment tools and software development. Typically, a company seekinga new application can engage a software developer to develop the newsoftware application for based on specifications or other methodology.

As generally understood, the conventional approach for developing acustom software application is to engage designers to develop theinterface designs, the visual components, and software developers toimplement the customer requirements for the software applicationincluding the design aspect into working source and object code (e.g.,adapted for selected operating systems). The interactions with thesoftware developer may involve initial conversations, artwork, or inputfrom designers, source code developers, and customers. The interactioncan result in deficiencies in efficiency, pricing, implementation, andconsistency.

This process can often times result in projects dying because of thecomplexity and the extended time for development. Techniques forimproving this process, which can improve the design and developmentprocess and provide greater efficiencies for vendors and customers alongwith the platform, are desired.

Conventional systems lack robustness in the provided tools that canreliably improve the design creation a new customer application andimprove the efficiency of the build.

Overall, there can be one or more technical problems related to softwaredevelopment.

SUMMARY OF THE INVENTION

According to embodiments of the present invention, an online softwaredevelopment platform providing an integrated resource for design,development, and purchase of customer-desired software applications forsoftware projects created by customers can be provided. A platform withfewer or additional features are contemplated in some embodiments. Theplatform can form example comprise one or more computers configuredusing computer readable instructions stored in non-transitory computermemory to provide the software development platform, wherein thesoftware development platform is configured to implement a plurality ofelectronic operational domains providing user-interactive capabilitiesor internal functionalities of the software development platform.

The domains can comprise a project scope process that is configured toprovide a user with the ability through interactive display screens tospecify and accept a scope for the software project, wherein as part ofthe project scope process through interactive screens the user creates aproject and selects a plurality of features to be in the project; apricing process that is configured to evaluate the software project anddetermine price for the delivery of a software application for thesoftware project; and a project development process that is configuredto selectively assign one or more elements of the software project,including one or of the selected features for the project, to developersand manage and track the development process.

The software development platform is configured to collect data fromactivity in the project scope process, pricing process, and projectdevelopment process in accordance with platform-defined graph datastructures, wherein the graph data structures comprising (a) a pluralityof different types of nodes representing entities, the node typescomprising template, project, and feature, each node type having a setof defined attributes, and different types of edges that representinterrelationship between entities.

The software development platform is configured to generate and store agraph database comprising the nodes and edges created from the collecteddata in the operation of software development platform and configured toreuse existing nodes and edges, add new nodes and edges, and adjustindividual attributes of existing nodes and edges, wherein the graphdatabase represents via nodes and edges an aggregation of the softwareprojects conducted on the software development platform and relatedinformation and is updated to include new software projects usingcollected data.

The software development platform is configured to, in response to aquery of the nodes and edges, control one or more parts of the operationof the platform.

The software development platform can be configured to traverse nodesand edges and stop travel to identify one or paths comprising connectednode and edge paths in the graph database in accordance with a graphtraversal algorithm, wherein the platform stops traversal when acriterion of the algorithm is not found.

The software development platform wherein the platform is configured, inresponse to the query, to control a user interaction in the projectscoping process comprising displaying an option that suggests a featureto include based on the structure of the graph database.

The software development platform wherein the platform comprises aknowledge graph process wherein the platform is configured tocontinuously collect data and add nodes and edges to the graph databaseusing the collected data, store the graph database in a first location,periodically perform a script that copies the graph database, loads thecopied graph database to a second location, and interacts with thecopied knowledge graph as part of the operation of the project scopeprocess to provide software tools based on the knowledge graph.

The software development platform wherein the platform is configured toinclude embedding generation that generates an embedding comprising aplurality of n-dimensional vectors that in accordance with an embeddingalgorithm represent the graph database, each n-dimensional vectorcorresponding to a node in the graph database and comprising vectorvalues based on relationship to other nodes in the graph database.

The software development platform wherein the platform is configured tostore a plurality of different hyper parameters corresponding todifferent software tools on the platform.

The software development platform wherein the platform is configured tocontrol the embedding generation with the hyper parameters and generatedifferent and store different embeddings corresponding to differentsoftware tools.

The software development platform wherein the query is applied to theembedding to generate an output for the control of an operation,display, or recommendation.

The software development platform wherein the software tool suggests afeature to add to the software project based on the embedding.

Other controls and tools are contemplated.

Embodiments of the present invention include methods (including relatedsystems or computer readable medium) for creating software. Suchembodiments can include receiving input from a customer, by a serverrunning a software creating component, the input describing at least oneaspect of a software program, determining, by the software creatingcomponent based on the input, existing code components that may be usedto create the software program, the existing code components beingstored in a code library accessible by the software creating component,determining, by the software creating component based on the user inputand based on the existing code components that may be used to create thesoftware program, new code components that must be developed for thesoftware program, and providing, by the software creating component tothe user, a cost estimate for the software program based on the existingcode components that may be used and based on the new code componentsthat must be developed. The methods can include adjusting the costestimate based on the at least one aspect of the software program. Themethods can include at least one aspect of the software programincluding at least one of: a platform category, an application template,a requirement collection, a platform, a number of screens, a feature, ateam location, a time to market, and a build depth. The build depth caninclude a wireframe, a design, a navigable prototype, a minimal viableproduct, or a complete project. The methods can include sending, by thesoftware creating program, a set of existing code requirement and a setof new code requirements to a team selector, and generating, by thesoftware creating program, a build card based on the existing codecomponents that may be used and based on the new code components thatmust be developed. The methods can include generating, by the softwarecreating program, a project schedule based at least in part on the buildcard, the project schedule including events related to the creation ofthe software program, and managing, by the software creating program,the events related to the creation of the software program. The eventsrelated to the creation of the software program including at least oneof: a project milestone; a code commit; and a customer message. Themethods further comprising passing, by the software creating program, atleast one event ID to a communication program, and sending, by thecommunication program, a message to the customer based on the event ID.The methods can include receiving, by a communication program, a messagefrom the customer; and parsing, by the communication program, thereceived message into the software creating program.

BRIEF DESCRIPTION OF THE DRAWINGS

Various features of examples and embodiments in accordance with theprinciples described herein may be more readily understood withreference to the following detailed description taken in conjunctionwith the accompanying drawings, where like reference numerals designatelike structural elements, and in which:

FIG. 1 is a simplified block diagram of a distributed computer networkaccording to an embodiment of the present invention;

FIG. 2 shows an exemplary computer system such as a client systemaccording to an embodiment of the present invention;

FIG. 3A is a simplified block diagram of an embodiment of a system forcreating software;

FIG. 3B illustrates a functional block diagram of an online softwaredevelopment platform according to an embodiment of the presentinvention;

FIG. 4 is a diagram showing a block diagram of aspects of systemarchitecture of an embodiment for creating software, i.e., decisiontriggers and user flow, and a block diagram illustrating back endcomponents of an embodiment for creating software;

FIGS. 5-10 describe and illustrate aspects of the problem and thesolution to the problem provided by embodiments of the systems andmethods;

FIGS. 11-12 describe and illustrate aspects of how the user acquiresaccess to embodiments and aspects of the value provided by embodimentsof the systems and methods;

FIG. 13 is a block diagram illustrating an overview of an embodiment forcreating software;

FIG. 14 is a block diagram illustrating a project scope and pricingprocess of an embodiment for creating software;

FIG. 15 is a block diagram illustrating a code selection and integrationprocess of an embodiment for creating software;

FIG. 16 is a block diagram illustrating a project development process ofan embodiment for creating software;

FIG. 17 is a block diagram illustrating a customer relationship andmanagement process of an embodiment for creating software;

FIGS. 18-37 describe and illustrate a user experience and flow usingscreenshots from a user interface of an embodiment for creatingsoftware;

FIGS. 38-43 describe and illustrate an administrative user interface andflow using screenshots of an embodiment for creating software;

FIG. 44 illustrates a visual representation of a graph databaseaccording to an embodiment of the present invention;

FIG. 45 illustrates a visual representation of different nodes types inthe graph database according to an embodiment of the present invention;

FIG. 46 is an illustrative functional block diagram of knowledge graphbased recommendation tool according to an embodiment of the presentinvention;

FIG. 47 illustrates a visual representation of a new build card andrelation to graph database for illustrative recommendation toolaccording to an embodiment of the present invention;

FIG. 48 is a functional block diagram for producing, updating, andmaking the graph database live in the system according to an embodimentof the present invention;

FIG. 49 is a functional block diagram for a knowledge graphincorporating node embedding into the tool according to an embodiment ofthe present invention;

FIG. 50 is an illustrative method for providing node embedding accordingto an embodiment of the present invention;

FIG. 51 is an illustrative method for generating a score andrecommending a feature according to an embodiment of the presentinvention;

FIG. 52 illustrates an interface of the software application accordingto an embodiment of the present invention;

FIG. 53 illustrates an interface for using templates in the designprocess according to an embodiment of the present invention;

FIG. 54 illustrates an interface for using a problem/problem group inthe design process according to an embodiment of the present invention;and

FIG. 55 illustrates ones type of interface or interaction with the userin which the platform provides one or more feature recommendations tothe user according to an embodiment of the present invention.

Certain examples and embodiments have other features that are one of inaddition to and in lieu of the features illustrated in theabove-referenced figures. These and other features are detailed belowwith reference to the above-referenced figures.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments of the present invention disclose a system and method thatautomate aspects of developing software applications. Embodiments of thepresent invention involve creating a graph or graph database thatinvolves a computer system that is configured to collect discreteinformation as defined nodes and edges as part of this process. Forexample, a software development platform can be configured to include aninteractive online interface for receiving a customer softwareapplication project and engage in that process to completion. Theplatform can provide an engagement process in which the customer throughinteractive software interactions (or possibly sometimes humaninteraction in some instances) can specify the functionality andoperating characteristics of the desired software application. Theplatform can include selected features, manually or automatically, thatwork through the software development process with the customer and isconfigured to operate to develop the software for the customer throughthe use of a team of software developers and other included software andhardware infrastructure. In some embodiments, the platform is configuredto automatically generate the software application or to combine the useof developer with the automatic generation of the software application.

The platform can handle different types or categories of applicationsand be configured to accept, for example, many projects. An advancementthat can make a material and significant improvement is that theplatform can be configured with defined nodes and edges that correspondto entities and relationship. The nodes and edges are used to create agraph database representing the information that is being collected bythe software application development platform. The resulting graphdatabase provides more advanced, faster, granular, predictive, and moreaccurate system for tools or features within the software developmentfield and the platform. The structure of the graph schema and graphdatabase provides improvements in speed such as to provide real timeresponses that are not otherwise possible using conventional solutionsin this field of technology (software development platforms). Thisincorporation materially improves the functionality of the platform andthe development process through capitalizing in identifying valuablepathways and interrelationships that are discovered from the graph.

As illustrated herein as examples which can by themselves beparticularly suitable for use. Nodes can be defined by the platform forexample as the following types: template, build card, developer,feature, problem statement, and CPE/CTE (client product expert/clienttechnical expert). Nodes can have predefined attributes such ascomplexity, price, or time, the value for which can be added to the nodeby the platform based on customer interaction, by an automated process,or by tracking actual performance such as tracking a project andautomatically entering the time when a feature was completed. Edges canbe defined to describe a limited set of relationships between nodes. Alimited set of edges can be defined to categorize different types ofnode-node interrelationships. Illustrative or examples of information isprovided in the figures of edges, which can also be particularlyvaluable in implementation. This structure of nodes and edges can allowthe platform to automatically and in a uniformly consistent way ingestthe (end to end) software development process (including a range ofattributes such as prices, timeline, skills, etc.) as carried outthrough the platform and are quickly defined for progress in to the nextphase of development.

The platform through aggregation creates, stores, and updates the graphdatabase including the nodes and edges as per the definedcharacteristics of the nodes and edges. The resultant graph throughaggregation can result in a highly valuable resource in improving theplatform and software development such as by providing softwareapplications that have fewer bugs.

The system can be configured to permit different types of softwarequeries and propagation to provide different features such as toautomate platform features and support software development and platformoperation. For example, as shown herein, a feature can define a node anda range of software features can be saved as nodes in the graphdatabase. The system can store edges, among which it can store edgesthat specify that each project has an edge to another feature node whenthose two feature were included in the same software developmentproject. This can for example be accumulated for many projects (e.g.,thousands, hundreds of thousands, etc.). Because each project mayinclude many different features, the resulting node interrelationshipcan be complex in a large order of magnitude. The features can haveedges to other types of nodes such as developer nodes for the specificdeveloper that developed that feature for that project.

As a base case, the node/edge relationship captured for features inprojects can be queried. For example, a potential new project has beenselected (e.g., by a client) to include three different features from amenu to be included in the client's project. The platform can query thegraph database and the selected features can be applied as a query tothe graph database that in response will for example traverse onlythrough paths that includes the select three nodes, and will furthertraverse those subgraphs in the found paths that contains the threenodes to identify other nodes that are connected to all three of thosenodes (when all three of those nodes were included in another project).A query to the graph database can also involve a query to an embeddinggenerated from the graph database and representing the graph structurein computer operationally simpler construction. The query may furtherestablish an algorithm that may filter nodes that are found through thetraversal to a set that meets a threshold (e.g., this fourth node wasincluded every time these three nodes were include, or this fourth nodewas include a large percentage of the time) indicating a likelihood ofvaluable software development and functional affiliation. To amplify,this can involve 10 selected features and can also include variationswhere the query is varied to find any 9 of the selected features andthen identify the related nodes in that path for use in the platform asa suggestion or automatic incorporation. Other analysis at the samelevel or more complex can be obtained quickly with reliable predictionsbased on the aggregated graph and the values of nodes and edges. Oneintuitive value is that providing reliable information to clients canprovide higher level of credulity and trust. It can also provide bettersoftware performance since available features (catalogue of features onthe platform) are automatically scored and included in properassociation (such as for a particular new project).

If desired, the system may have a visual interface that permits user tointeract with the nodes and edges (e.g., to apply a query) but such afeature is not required.

The platform can be a cloud service that permits the user to interactwith the platform through graphical user interfaces to complete thedifferent stages of the application development process. That wouldgenerally be understood to involve a combination of one or morecomputers, software implemented on the one or more computers thatconfigures the computers to provide a specialized application, andonline, Internet website access, to the functionality through a(conventional) browser or in some cases, a software application (e.g., amobile app). The platform or system can be structured to define featuresas individual elements having certain characteristics such as meta data.A feature is further defined herein.

In preferred embodiments, the platform is an online software developmentplatform that is used by the public to engage a company to develop aparticular software application for the customer. An example of such asystem is illustratively described in U.S. Patent Publication No.20180107459, by Dugal et al., filed Oct. 17, 2017, which is incorporatedherein by reference in its entirety. The platform is preferablyconfigured to provide the user, a potential customer, with the abilityto interact with different interactive user interfaces (display screens,which can refer to a portion of a displayed screen or graphical userinterface) to intuitively specify the requirements for the desiredcustom software application. The platform can be configured to operateas an application in object code that interacts with the user. Theplatform preferably includes a repository of existing source code forindividual features that have been previously collected, used and/ortested to implement a corresponding feature. This source code can bereused, modified or compiled during the software development to producethe actual software application sought by the user. Thus, the system isconfigured to maintain different modes of a feature and one that is thesource code for the actual feature for use in developed application, andone that names the feature and defines associated meta data (and/orlinks (e.g., connect using pointers to other features).

The platform can also include a subsystem that communicates with a setof third party software developers to communicate the requirements (viamessaging) and to engage the developers to develop additional sourcecode or desired modification that after a query to the existing databaseof feature source code is determined to be needed or unavailable in therepository, thus requiring the developers to create new code forrequirements or selections that are not in the repository (which iscommunicated via the platform).

The platform can also communicate the requirements internally viaelectrical communications and in response automatically generate orassemble source code that contains the source code for the selectedfeatures from the repository. The repository can store different versionof the source code such as for different operating system or differentend use platforms (e.g., mobile phones versus laptops). As part of thesoftware development process, the platform can display interfaces thatrequire the user to select the operating system and end user platform.If desired, the platform takes that selection into account in generatingor assembling source code for a customer's actual application.

The platform can be configured to allow the user to select the desiredfeatures as a preliminary step in order to specify the requirements forthe desired custom software application (the scope of the softwareproject).

The platform can therefore be configured for the user to perform thedesign process or a portion thereof, e.g., on its own without the needto involve designers or third party user interface design applications,and to have a general initial (mutual) understanding of expectation andscope through this process. The platform can preferably provide the userwith an integrated resource for design with a streamlined process forsoftware development where there is preexisting common structure betweendesign and development such as by way of correspondence between featuresand corresponding source code, for the actual software, that is part ofthe platform.

FIG. 1 is a simplified block diagram of a distributed computer network100 incorporating an embodiment of the present invention. Computernetwork 100 includes a number of client systems 105, 110, and 115, and aserver system 120 coupled to a communication network 125 via a pluralityof communication links 130. Communication network 125 provides amechanism for allowing the various components of distributed network 100to communicate and exchange information with each other.

Communication network 125 may itself be comprised of many interconnectedcomputer systems and communication links. Communication links 130 may behardwire links, optical links, satellite or other wirelesscommunications links, wave propagation links, or any other mechanismsfor communication of information. Various communication protocols may beused to facilitate communication between the various systems shown inFIG. 1 . These communication protocols may include TCP/IP, HTTPprotocols, wireless application protocol (WAP), vendor-specificprotocols, customized protocols, and others. While in one embodiment,communication network 125 is the Internet, in other embodiments,communication network 125 may be any suitable communication networkincluding a local area network (LAN), a wide area network (WAN), awireless network, an intranet, a private network, a public network, aswitched network, Internet telephony, IP telephony, digital voice, voiceover broadband (VoBB), broadband telephony, Voice over IP (VoIP), publicswitched telephone network (PSTN), and combinations of these, and thelike.

System 100 in FIG. 1 is merely illustrative of an embodiment and doesnot limit the scope of the systems and methods as recited in the claims.One of ordinary skill in the art would recognize other variations,modifications, and alternatives. For example, more than one serversystem 120 may be connected to communication network 125. As anotherexample, a number of client systems 105, 110, and 115 may be coupled tocommunication network 125 via an access provider (not shown) or via someother server system. An instance of a server system 120 and a computingdevice 105 may be part of the same or a different hardware system. Aninstance of a server system 120 may be operated by a provider differentfrom an organization operating an embodiment of a system for specifyingan object in a design, or may be operated by the same organizationoperating an embodiment of a system for specifying an object in adesign.

Client systems 105, 110, and 115 typically request information from aserver system which provides the information. Server systems bydefinition typically have more computing and storage capacity thanclient systems. However, a particular computer system may act as both aclient and a server depending on whether the computer system isrequesting or providing information. Aspects of the system may beembodied using a client-server environment or a cloud-cloud computingenvironment.

Server 120 is responsible for receiving information requests from clientsystems 105, 110, and 115, performing processing required to satisfy therequests, and for forwarding the results corresponding to the requestsback to the requesting client system. The processing required to satisfythe request may be performed by server system 120 or may alternativelybe delegated to other servers connected to communication network 125.

Client systems 105, 110, and 115 enable users to access and queryinformation or applications stored by server system 120. Some exampleclient systems include portable electronic devices (e.g., mobilecommunication devices) such as the Apple iPhone®, the Apple, or anydevice running the Apple iOS™, Android™ OS, Google Chrome OS, SymbianOS®, or Windows Mobile® OS. In a specific embodiment, a “web browser”application executing on a client system enables users to select,access, retrieve, or query information and/or applications stored byserver system 120. Examples of web browsers include the Android browserprovided by Google, the Safari® browser provided by Apple, the Opera Webbrowser provided by Opera Software, and Internet Explorer Mobilebrowsers provided by Microsoft Corporation, the Firefox® and Firefox forMobile browsers provided by Mozilla®, and others.

FIG. 2 shows an exemplary computer system such as a client system ofembodiments of the present invention. In an embodiment, a userinterfaces with the system through a client system, such as shown inFIG. 2 . Mobile client communication or portable electronic device 200includes a display, screen, or monitor 205, housing 210, and inputdevice 215. Housing 210 houses familiar computer components, some ofwhich are not shown, such as a processor 220, memory 225, battery 230,speaker, transceiver, antenna 235, microphone, ports, jacks, connectors,camera, input/output (I/O) controller, display adapter, networkinterface, mass storage devices 240, and the like. Computer system 200may include a bus or other communication mechanism for communicatinginformation between components. Mass storage devices 240 may store auser application and system software components. Memory 225 may storeinformation and instructions to be executed by processor 220.

Input device 215 may also include a touchscreen (e.g., resistive,surface acoustic wave, capacitive sensing, infrared, optical imaging,dispersive signal, or acoustic pulse recognition), keyboard (e.g.,electronic keyboard or physical keyboard), buttons, switches, stylus,gestural interface (contact or non-contact gestures), biometric inputsensors, or combinations of these.

Mass storage devices 240 may include flash and other nonvolatilesolid-state storage or solid-state drive (SSD), such as a flash drive,flash memory, or USB flash drive. Other examples of mass storage includemass disk drives, floppy disks, magnetic disks, optical disks,magneto-optical disks, fixed disks, hard disks, CD-ROMs, recordable CDs,DVDs, recordable DVDs (e.g., DVD-R, DVD+R, DVD-RW, DVD+RW, HD-DVD, orBlu-ray Disc), battery-backed-up volatile memory, tape storage, reader,and other similar media, and combinations of these.

System 100 may also be used with computer systems having differentconfigurations, e.g., with additional or fewer subsystems. For example,a computer system could include more than one processor (i.e., amultiprocessor system, which may permit parallel processing ofinformation) or a system may include a cache memory. The computer systemshown in FIG. 2 is but an example of a computer system suitable for use.Other configurations of subsystems suitable for use will be readilyapparent to one of ordinary skill in the art. For example, in a specificimplementation, the computing device is mobile communication device suchas a smartphone or tablet computer. Some specific examples ofsmartphones include the Droid Incredible and Google Nexus One®, providedby HTC Corporation, the iPhone® or iPad®, both provided by Apple, andmany others. The computing device may be a laptop or a netbook. Inanother specific implementation, the computing device is a non-portablecomputing device such as a desktop computer or workstation.

A computer-implemented or computer-executable version of the programinstructions useful to practice the present invention may be embodiedusing, stored on, or associated with computer-readable medium. Acomputer-readable medium may include any medium that participates inproviding instructions to one or more processors for execution. Such amedium may take many forms including, but not limited to, nonvolatile,volatile, and transmission media. Nonvolatile media includes, forexample, flash memory, or optical or magnetic disks. Volatile mediaincludes static or dynamic memory, such as cache memory or RAM.Transmission media includes coaxial cables, copper wire, fiber opticlines, and wires arranged in a bus. Transmission media can also take theform of electromagnetic, radio frequency, acoustic, or light waves, suchas those generated during radio wave and infrared data communications.

For example, a binary, machine-executable version, of the softwareuseful to practice embodiments of the present invention may be stored orreside in RAM or cache memory, or on mass storage device 240. The sourcecode of this software may also be stored or reside on mass storagedevice 240 (e.g., flash drive, hard disk, magnetic disk, tape, orCD-ROM). As a further example, code useful for practicing embodiments ofthe invention may be transmitted via wires, radio waves, or through anetwork such as the Internet. In another specific embodiment, a computerprogram product including a variety of software program code toimplement features of embodiments of the invention is provided.

Computer software products may be written in any of various suitableprogramming languages, such as C, C++, C #, Pascal, Fortran, Perl,Matlab (from MathWorks, www.mathworks.com), SAS, SPSS, JavaScript,CoffeeScript, Objective-C, Objective-J, Ruby, Python, Erlang, Lisp,Scala, Clojure, and Java. The computer software product may be anindependent application with data input and data display modules.Alternatively, the computer software products may be classes that may beinstantiated as distributed objects. The computer software products mayalso be component software such as Java Beans (from Oracle) orEnterprise Java Beans (EJB from Oracle).

An operating system for the system may be the Android operating system,iPhone OS (i.e., iOS), Symbian, BlackBerry OS, Palm web OS, bada, MeeGo,Maemo, Limo, or Brew OS. Other examples of operating systems include oneof the Microsoft Windows family of operating systems (e.g., Windows 95,98, Me, Windows NT, Windows 2000, Windows XP, Windows XP x64 Edition,Windows Vista, Windows 7, Windows CE, Windows Mobile, Windows Phone 7),Linux, HP-UX, UNIX, Sun OS, Solaris, Mac OS X, Alpha OS, AIX, IRIX32, orIRIX64. Other operating systems may be used.

Furthermore, the computer may be connected to a network and mayinterface to other computers using this network. The network may be anintranet, internet, or the Internet, among others. The network may be awired network (e.g., using copper), telephone network, packet network,an optical network (e.g., using optical fiber), or a wireless network,or any combination of these. For example, data and other information maybe passed between the computer and components (or steps) of a systemuseful in practicing the invention using a wireless network employing aprotocol such as Wi-Fi (IEEE standards 802.11, 802.11a, 802.11b,802.11e, 802.11g, 802.11i, and 802.11n, just to name a few examples).For example, signals from a computer may be transferred, at least inpart, wirelessly to components or other computers.

FIG. 3A is a simplified block diagram of an embodiment of a system 300for creating software for use by a user 301. System 300 includes one ormore user computing devices 305, and a server 320, coupled to acommunication network 325 via a plurality of communication links 330.Computing device 305 may be used to run a user application 310 forcreating software from existing code and new code. User application 310may use computing device 305 and network 325 to access server 320.Communication network 325 (or “network 325”) provides a mechanism forallowing the various components of system 300 to communicate andexchange information with each other via communication links 330. Server320 may include or have access to a database 340 of code libraries 342a, 342 b, . . . , 342 n. Each code library includes software code (notshown) from which system 300 may select to create customized software.Each code library 342 a, 342 b, . . . , 342 n may have selected from ita subset of code sections 345 a, 345 b, . . . , 345 n, which server 320may assemble into customized software 350 a, 350 b, . . . , 350 n andprovide to user 301 via computing device 305. Customized software may becomplete or may need to be augmented with additional custom codesections that may be newly created by partner developers. Server 320 oran administrator may combine or integrate newly created code withexisting code sections to create customized software.

Computing device 305 may run a software-creating component 315 which maybe provided with a subset of code sections (e.g., subset 345 a fromserver 320 via user application 310) that software-creating component315 (like server 320) may assemble into customized software (e.g.,customized software 350 a).

Network 325 may be any suitable communications network. Communicationnetwork 325 may itself be comprised of many interconnected computersystems and communication links. As an example and not by way oflimitation, one or more portions of network 325 may include an ad hocnetwork, an intranet, an extranet, a virtual private network (VPN), alocal area network (LAN), a wireless LAN (WLAN), a wide area network(WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), aportion of the Internet, a portion of the Public Switched TelephoneNetwork (PSTN), a cellular telephone network, another suitable network,or a combination of two or more of these. Network 325 may include one ormore networks 325.

Connections 330 may connect computing device 305 and server 320 tocommunication network 325 or to each other. Communication links 330 maybe hardwire links, optical links, satellite or other wirelesscommunications links, wave propagation links, or any other mechanismsfor communication of information. This disclosure contemplates anysuitable connections 325. In particular embodiments, one or moreconnections 325 include one or more wireline (such as for exampleDigital Subscriber Line (DSL) or Data Over Cable Service InterfaceSpecification (DOCSIS)), wireless (such as for example Wi-Fi orWorldwide Interoperability for Microwave Access (WiMAX)) or optical(such as for example Synchronous Optical Network (SONET) or SynchronousDigital Hierarchy (SDH)) connections. In particular embodiments, one ormore connections 330 each include an ad hoc network, an intranet, anextranet, a VPN, a LAN, a WLAN, a WAN, a WWAN, a MAN, a portion of theInternet, a portion of the PSTN, a cellular telephone network, anothersuitable connection 330, or a combination of two or more suchconnections 330. Connections 330 need not necessarily be the samethroughout system 300. One or more first connections 330 may differ inone or more respects from one or more second connections 330.

Server 320 may be a network-addressable computing system that can hostone or more product databases 340. Server 320 may be responsible forreceiving information requests from computing device 305 via userapplication 310, for performing the processing required to satisfy therequests, for generating responses (e.g., custom software 350 a, . . . ,350 n) to received inquiries, and for forwarding the resultscorresponding to the requests back to requesting computing device 305.Server 320 may store, receive, or transmit data and software, andinformation associated with the data and software (including user data).The processing required to satisfy the requests may be performed byserver 320 or may alternatively be delegated to other servers connectedto communication network 325. For example, other servers may hostdatabase 340, or have additional databases. Server 320 may be anintermediary in communications between a computing device 305 andanother server system, or a computing device 305 may communicatedirectly with another server system. Server 320 may be accessed by theother components of system 300, for example, directly or via network325. In particular embodiments, one or more users 301 may use one ormore computer devices 305 to access, send data to, and receive data fromserver 320.

Computing device 305, connections 330, and network 325, enable user 301to access and query information stored and applications run by server320, such as database 340. Some example computer devices 305 includedesktop computers, portable electronic devices (e.g., mobilecommunication devices, smartphones, tablet computers, laptops) such asthe Samsung Galaxy Tab®, Google Nexus devices, Amazon Kindle®, KindleFire®, Apple iPhone®, the Apple iPad®, Microsoft Surface®, the PalmPre™, or any device running the Apple iOS®, Android® OS, Google Chrome®OS, Symbian OS®, Windows Mobile® OS, Windows Phone, BlackBerry® OS,Embedded Linux, Tizen, Sailfish, webOS, Palm OS® or Palm Web OS®.

In an embodiment, user application 310 may be run or executed by adifferent system. For example, computing device 305, or server 320, orboth, may run user application 310. That is, user application 310 may berun by computing device 305, or the application may be run on server 320and accessed by computing device 305 through a browser and network 325.For example, computing device 305 could be operated as a terminal, withuser application 310 being run on a server, e.g., server 320. In anembodiment, aspects or functionalities of user application 310 are runby server 320, or another computing system or server. In an embodiment,the steps of the methods described herein may be performed, at least inpart, in cloud-computing environment.

FIG. 3A illustrates a particular arrangement of user 301, computingdevice 305, and server 320, but this is an example arrangement. Anyother suitable arrangement of user 301, computing device 305, server320, and network 325 may be used. For example, computing device 305 maybe connected directly to server 320. Also, computing device 305 andserver 320 may appear to be distinct yet operate on the same hardware.In addition, any number of users 301, clients 305, and server 320 may beused in embodiments.

FIG. 4 is a diagram showing block diagrams of system architecture of anembodiment for creating software.

In an embodiment, a method for creating software is called“Engineer.ai.”

Why was Engineer.ai created? Engineer.ai was created to allow for thebuilding of digital products at least 30% faster and for 30% less thananyone else in the industry, all while guaranteeing top quality.

What is it and how does it work? Engineer.ai is an “as-a-service”platform for software outsourcing, turning App Development/SoftwareOutsourcing into something as simple as a restaurant menu that you canpick a-la carte. This includes an On-Demand & Online Price Calculatorfor building any digital product from a Wearable to a Marketplace to anApp with price guarantees, and intelligent automation/machine assistancethat reduces the average cost and time of any project by at least30%-40%. Engineer.ai offers a transparent fixed price upfront. Nosurprises and any amount over your fixed price is waived.

How does the service/product work? Engineer.ai provides an intuitive andeasy-to-use wizard for pricing any idea in less than 60 seconds withpre-set options made available based on the project type. The fixedprice you get is offered immediately and upfront. You don't need to waitor speak to a salesperson to know exactly what your project will costand how long it will take to deliver.

How is my project managed? Engineer.ai provides weekly updates so youalways know the exact status of your project. Engineer.ai practices goldstandard for coding so quality is never sacrificed. Engineer.ai offers aweekly subscription and billing model so you are never locked in and canpause, speed up, or walk away at anytime.

Engineer.ai Benefits

-   1) Build your idea for 30% less and 30% faster than your    competitors.-   2) Use our easy-to-use wizard for pricing any idea in less than 60    seconds.-   3) Get transparent and fixed pricing for your project upfront and    instantaneously without speaking to a sales rep.-   4) Have the confidence your project will be delivered on time and    will not go over budget.-   5) If you are not sure what you want, use our wizard to build out    your idea by choosing from a bundle of pre-set options.

Engineer.ai Description

Engineer.ai uses machines to automate and institutionalize as much ofthe software outsourcing process as possible. Engineer.ai includestransparent pricing, standardized delivery, and a manufacturing-styledapproach to development that reuses an estimated 50% of code and designthat is often standardized and duplicated across many apps and digitalplatforms.

A key part of our business model is how Engineer.ai actually scales andbuilds. Engineer.ai scales by using 3rd party dev shops/contractors andhaving them deliver under the Engineer.ai brand, and Engineer.ai usescode libraries. Similarly Engineer.ai lets Software Companies getpredictable revenue, a framework that lets them get paid and a way forthem to access our rich code libraries & SIMBA Platform (Simple,Integrated, Machine-Based, Architecture Platform). Engineer.ai alsoscales by the institutionalization of the Engineer.ai code anddevelopment process.

SIMBA connects the entire product delivery process together. Itintegrates on-boarding, pricing, engineering and product/projectmanagement using machine-learning processing and A.I. (“artificialintelligence”) to keep constant conversation with the customer. Aspectsof SIMBA include:

-   -   A “Pick-n-mix” wizard for pricing any idea.    -   A weekly subscription with max price guarantee.    -   A learning algorithm for real-time pricing.    -   A machine-created templates from code library for efficient &        consistent delivery.    -   And an automated project and progress reports to ensure that        customers have transparency in pricing, financial control, and        automation

Engineer.ai is the first service to unify Development Shops around theworld:

-   -   First published pricing platform that lets your price an app or        an idea within 30 seconds online.    -   First process-driven and machine-led manufacturing approach for        building software in a “just-in-time” model.    -   First use of machine-learning and Artificial Intelligence in        machines and BOTs (software applications that run automated        tasks (scripts) over the Internet) to automate the product        delivery process.    -   For areas Engineer.ai feels need more “business interest,”        Engineer.ai may subsidize the development, such as efforts with        content-led marketplaces; Engineer.ai can effectively invest in        customers by simply offsetting some of its fees.

Role of SIMBA in Engineering.ai:

-   -   Automated Pricing    -   Machine-assisted product management    -   Code creation

Engineer.ai—Features

1) Project selector

-   -   a) Category selection        -   i) Current categories        -   ii) Option for more categories        -   iii) Metrics to track selection and % completion    -   b) Template type    -   c) Other project description (outside selector parameters)    -   d) Platforms    -   e) Feature preview    -   f) Portfolio examples    -   g) Team location    -   h) Dev speed (time to market)    -   i) Build fidelity        2) Pricing estimate    -   a) Real time projected cost based on project guidelines created        in the selector        3) Customer contact capture & confirmation    -   a) Project review (can user adjust here?)    -   b) Customer contact collected    -   c) Saved confirmation of submission via email

Engineer.ai—Additional Features

1) Project estimator additional features

-   -   a) Wireframe database    -   b) Intelligence re: additional categories & dataset    -   c) Mobile & touch friendly    -   d) Workflow for customer/sales interaction    -   e) In an embodiment, the method makes a decision based on        historical variance. For example, if there is some customization        required for a particular type of app, and if the type of app        shows a historical cost variation, the method adjusts the        potential customization cost based on the historical variation.        2) Payment & contract execution    -   a) Proposal automation        -   i) Proposal based on integration (the degree and depth of            integration)    -   b) Billed deposit and weekly, monthly invoice    -   c) Pay from invoice

3) Design

-   -   a) Goal to assign to the right designer    -   b) Preview based on component elements & wireframes    -   c) Map to design library    -   d) 2-3 week iteration with customer (details?)        4) Project team assignment    -   a) Semi-automated    -   b) Track team member status & availability projection        5) Component user story generation    -   a) Board creation    -   b) Database of tagged stories    -   c) Feature based story selection        6) Base code generation    -   a) Code pods    -   b) Feature based pod selection        7) Sprint estimator    -   a) Feature/team/speed based estimation of completion    -   b) Automated notifications of progress, potential deadline        extensions, and sprint completions

Engineer.ai—Partner Development Qualification Process

1) Sources

-   -   a) Inbound        -   i) Website    -   b) Outbound    -   c) Referral

2) Pre-qualification

-   -   a) Minimum team requirements    -   b) Ideal candidate profile—measure fill rate success/skills,        experience, etc    -   c) Team profiling tool        -   i) Team members        -   ii) Skills (dev lang, years experience, code committed)        -   iii) Projects (associated projects)            3) Project review    -   a) Minimum project examples—Live products ideal    -   b) Customer testimonials        4) Code review    -   a) Standardized code submission    -   b) Submission, automated and manual review, and workflow process

TABLE 1 gives a description of pages from a website employingembodiments of a method for creating software from library and customcomponents. In TABLE 1, a particular webpage is identified by thecolumns: ID, Title, and Labels. A Description column includes adescription of the particular webpage and its function.

ID TITLE LABELS DESCRIPTION 129382929 Product homepage As a user when Inavigate to Engineer.ai's URL, I will Homepage/ be navigated to landingpage of Engineer.ai. Landing The Landing page will present 5 Main Cardoptions Page to choose from. 1. Mobile App 2. Blog/Website 3.Marketplace 4. Wearables 5. Others **Note:** The entire text on cardslike title, description etc. along with icons is **not hardcoded** andis available through backend. Please ignore text on all cards in thedesign references. See, e.g., the screenshot on FIG. 18 for designreference. 129383567 Homepage | homepage As a user, when I hover on thecards on the landing Card Hover page, then the Main card will move upand an overlay State card will reveal options related to the main card.I should also see two buttons - **Start** and **Know More**. **Note:**The entire text on cards like title, description etc. along with iconsis **not hardcoded** and is available through backend. Please ignoretext on all cards in the design references. See. e.g., the screenshot onFIG. 19 for design reference. 129446881 Homepage | homepage As a user,when I click on *Know more* button after Card Hover hovering on a card,there should be another overlay State | over the same card revealing thefull feature set that Know More are applicable for card being hoveredupon. The feature set list can be longer than the display area and thusneeds to be horizontally scrollable. A start button will also appearbelow the feature list. I can click on *Start* button and should be ableto follow story #129446683 There will be another button under start bythe name of *Portfolio Projects*. Clicking on it will work as describedin story #129447399 **Note:** The entire text on cards like title,description etc. along with icons is **not hardcoded** and is availablethrough backend. Please ignore text on all cards in the designreferences. See. e.g., the screenshot on FIG. 20 for design reference.129440667 Personalize personalize As a user, when I am navigated to thisscreen through Product | product the workflow defined in story#129521135, I should Select see the first section to select theplatforms I need to Platform support in my Product. This is the firststep towards personalization of my product. Below the applicableplatforms list, I should be able to see the number of screensanticipated in my product. A **Next** button appears below, clicking onwhich I should be able to follow story #129514959. This button getsenabled only when I have one or more options from all required fieldsselected in this section. **Note:** The entire text on cards like title,description etc. along with icons is **not hardcoded** and is availablethrough backend. Please ignore text on all cards in the designreferences. See, e.g., the screenshot on FIG. 27 for design reference.129515019 Personalize personalize As a user, when I am navigated to thisscreen through Product | product the workflow defined in story#129514959 (on click Select on next), the third section overlay shouldcome to top. Delivery This will allow me to select the team I want touse to Speed develop my product and is the third step towardspersonalization of my product. A back button will appear below to theheader clicking on which I will be navigated to Select Features story(#129514959) A **Next** button appears below, clicking on which I shouldbe able to follow story #129515169. This button gets enabled only when Ihave one or more options from all required fields selected in thissection. **Note:** The entire text on cards like title, description etc.along with icons is **not hardcoded** and is available through backend.Please ignore text on all cards in the design references. See, e.g., thescreenshot on FIG. 28 for design reference. 129515169 Personalizepersonalize As a user, when I am navigated to this screen throughProduct | product the workflow defined in story #129515019 (on clickSelect on next), the third section overlay should come to top. DeliveryThis will allow me to select the speed of delivery for Speed my productand is the fourth step towards personalization of my product. A backbutton will appear below to the header clicking on which I will benavigated to Select Features story (#129515019) A **Next** buttonappears below, clicking on which I should be able to follow story#129522065. This button gets enabled only when I have one or moreoptions from all required fields selected in this section. **Note:** Theentire text on cards like title, description etc. along with icons is**not hardcoded** and is available through backend. Please ignore texton all cards in the design references. See, e.g., the screenshot on FIG.30 for design reference. 129514959 Personalize personalize As a user,when I am navigated to this screen through Product | product theworkflow defined in story #129440667 (on click Select on next), thesecond section overlay should come to Features top. This will allow meto select the features I need to include in my Product and is the secondstep towards personalization of my product. A **Back Button** willappear below to the header clicking on which I will be navigated toSelect Platform & Pages story (#129440667) A **Next** button appearsbelow, clicking on which I should be able to follow story #129515019.This button gets enabled only when I have one or more options from allrequired fields selected in this section. **Note:** The entire text oncards like title, description etc. along with icons is **not hardcoded**and is available through backend. Please ignore text on all cards in thedesign references. See. e.g., the screenshot on FIG. 36 for designreference. 129446683 Product homepage, As a user, when I click on*Start* button from hover Type product state or additional cardoverlays, I should be Landing type navigated to a separate page whichwill show cards Page (Start based on the card selected on homepage. fromany Additionally, if I click on header section of this card, card on thesame workflow should be followed. Homepage) **Note:** The entire text oncards like title, description etc. along with icons is **not hardcoded**and is available through backend. Please ignore text on all cards in thedesign references. See, e.g., the screenshot on FIG. 35 for designreference. 129514073 Product product As a user, when I hover on a cardin Product Type Type Page | type page, the card should show the list ofplatforms that Card Hover are applicable for that product type. State A*Know more* button will also appear below the applicable platforms list.I can click on this button and should be able to follow story #129514203On clicking the header of this card, I should be able to follow story#129514387 **Note:** The entire text on cards like title, descriptionetc. along with icons is **not hardcoded** and is available throughbackend. Please ignore text on all cards in the design references. See,e.g., the screenshot on FIG. 26 for design reference. 129522743Personalize personalize As a user, when I am navigated to this screenthrough Product | product the workflow defined in story #129522065 (onclick Your Build on next), the build card should appear. This screenCard shows your selections through 4 cards as showcased in the designreference. It should display the following 4 cards in the given order: *Product Type with description * Platform, Screens and Features list *Team and Speed * Development Phases and Estimate A **Get in Touch**button appears inside the 4th card, clicking on which I should be ableto follow story #129522917. **Note:** The entire text on cards liketitle, description etc. along with icons is **not hardcoded** and isavailable through backend, unless stated otherwise. Please ignore texton all cards in the design references. See, e.g., the screenshot on FIG.33 for design reference. 129522065 Personalize personalize As a user,when I am navigated to this screen through Product | product theworkflow defined in story #129515169 (on click Select on next), thephase selection screen should appear. It Project is the final steptowards personalization of my Phases product and product developmentlifecycle. It should display the following 4 phases: * Design *Prototype * MVP * Full Build By default all the 4 phases will beselected. As a user, I should also be able to unselect the selectedcard(s) as many times and vice-versa. The estimate in header shouldupdate instantly based on the selections I am making. A **Next** buttonappears below, clicking on which I should be able to follow story#129522743. This button gets enabled only when I have one or moreoptions from all required fields selected in this section. **Note:** Theentire text on cards like title, description etc. along with icons is**not hardcoded** and is available through backend, unless statedotherwise. Please ignore text on all cards in the design references.See. e.g., the screenshot on FIG. 32 for design reference. 129514203Product product As a user, when I click on *Next* button on hovered TypePage | type card in Products page, I should be able to see the CardHover features I can request for. The card overlay that State | openedin previous view moves a bit up to Know More accommodate the list. Ifthe list requires more space than available in the display area, thelist should be horizontally paginated. A *Next* button will also appearbelow the applicable features list. I can click on this button andshould be able to follow story **Note:** The entire text on cards liketitle, description etc. along with icons is **not hardcoded** and isavailable through backend. Please ignore text on all cards in the designreferences. See, e.g., the screenshot on FIG. 20 for design reference.129757983 Add in Depending on what the user selects, the price shouldpricing constantly be updating in the top-right section of the componentnavbar 129521135 Create the personalize As a user, when I am navigatedto this screen through Personalize product the workflow defined in story#129514387, I should Product see a card that has 4 dynamic sectionsstacked over Page one another. These sections (in defined order) are *Select Platforms *(Hard Coded Label)* * Select Features *(Hard CodedLabel)* * Select Team *(Hard Coded Label)* * Select Speed *(Hard CodedLabel)* Initially, only the first section will be enabled and rest willbe disabled. As and when I keep selecting options in each section, thenext section in stack gets enabled. I can also navigate directly betweenall the enabled sections directly by clicking them. The selectedsections comes on top while others are visible in the background. Forlinear navigation between enabled sections, I should also be able to usethe Back and Next button in each sections. The first section should nothave a back button. **Note:** The most of the text in sections liketitle, description etc. along with icons is **not hardcoded** and isavailable through backend; unless stated otherwise. See, e.g., thescreenshot on FIG. 27. 129522917 Personalize personalize As a user, whenI am navigated to this screen through Product | product the workflowdefined in story #129522743 (on click Get in on “Get in Touch” button),the Get in Touch screen Touch should appear. This screen should allow meto enter Screen information in following fields: * Project Name (100Characters) * Project Description (150 Characters) * My email ID (75Characters) * My Name (50 Characters) Below these fields, there shouldbe a checkbox asking me to confirm that I agree to *Terms & Conditions*and *Privacy Policy* I can also request for a *“Non DisclosureAgreement” * through another link below the above checkbox. Lastly, Ishould be able to save the details and allow the team to connect withme. I should now be navigated to next screen which follows story#129523531. See, e.g., the screenshot on FIG. 34 for design reference.129525811 Show and As a user I would like to see a dynamic header in theupdate application. This header is visible when I click on Header Starton any of the main cards on the home screen. The header has 5 sections(Collapsed form) The header has 5 sections (Expanded form) * ProductType * Product Sub Type & Its description * Platform, Features, Team andSpeed * Phase * Estimate Each section/sub-section will be added toheader as and when user navigates to these pages/sections and makesnecessary selections on screen. Any update in these sections alsoinstantly update the header with new information. I can also click onHeader to see the expanded view. Please see the below design forreference for collapsed view See, e.g., the screenshot on FIG. 35 fordesign reference. 129514387 Product product As a user, when I click on*Next* button on hovered Type Page | type card in Products page, anoverlay will stack over Add product existing overlays and allow me toadd a description description about the kind of product that I want tobuild. The description cannot be longer than 50 characters. Alternately,I can reach here by clicking the card header on *Product Types* page atany point of time. A *Start* button appear below the text field. I canclick on this button and should be able to follow story #129440667**Note:** The entire text on cards like title, description etc. alongwith icons is **not hardcoded** and is available through backend. Pleaseignore text on all cards in the design references. See, e.g., thescreenshot on FIG. 37 for design reference. 129523531 Create thepersonalize As a user, when I am navigated to this screen throughConcierge product the workflow defined in story #129522917 (on clickpage on “Get in Touch” button), the Concierge screen should appear.Here, I should be able to post my queries and add attachments.**Attachment types TBD**. Lastly, I should be able to start anestimation for a new build which redirects me to homepage. 129447399Homepage | homepage, As a user, when I click on *Portfolio Projects*button Card Hover skip in know more section of a card on Home page, anew State | overlay will appear as showcased in the design Know Morereference. | Portfolio It should show a list of 4 customers and a fewtestimonials. The testimonials should be horizontally scrollable. Astart button will also appear below the feature list. I can click on*Start* button and should be able to follow story #129446683 **Note:**The entire text on cards like title, description etc. along with iconsis **not hardcoded** and is available through backend. Please ignoretext on all cards in the design references.

FIG. 3B illustrates a system for developing software according to anembodiment of the present invention. The system includes an applicationdevelopment software application 420 installed on an electronic device410 and a builder software application 440 implemented on one or moreservers 430. The electronic device 410 is preferably a desktop computerthat can communicate with server via mobile networks or other wirelessnetworks. Each of the electronic device and servers is a computer systemthat includes a microprocessor and volatile and non-volatile memory toconfigure the computer system. The computer system also includes anetwork connection interface that allows the computer system tocommunicate with another computer system over a network. Each softwareapplication may also be used independently or in conjunction withanother software application to strengthen or supplement functionalitiesof the other software application.

The builder application 440 installed on the server 430 maintains alibrary of features for a software application. The library of featuresmay be stored in a database 460. The builder application 440 isconfigured to transmit to the software development application on theclient computer 410 the library of features, to receive a selection of aset of features, integrate the selected features into an integratedbuild card. The builder application further maintains a graph database480.

The software development application 420 is configured to provide agraphical user interface that enables a customer to select and customizea set of features as part of a build card for building softwareapplication for a customer's project. In some embodiments, the softwaredevelopment application 420 is a web application provided by the builderapplication on the server and configured to run in a conventionalbrowser. In a preferred embodiment, the software development applicationis the conventional browser 420 configured to access an applicationdevelopment website provided by the server.

Feature database 640 can also include source code for each of theplurality of available features. The saved source code provides arepository of source code for available features that the platform canuse to generate object code for the actual application (e.g., based onthe selected operating system) and/or to send the source code to selectthird party software developers to perform desired integration ormodification based on customer specified requirements.

The builder application is organized into a plurality of processes thattogether provide an implement a comprehensive platform for customers todesign or specify project requirements, financial management of theprocess including determination or estimation of pricing, projectmanagement, customer relationship management, and other processes. Thebuilder application or platform can provide an integrated resource fordesign, development, purchase, and delivery of customer-desired softwareapplications for software projects created by customers. The softwaredevelopment platform is configured to implement a plurality ofelectronic operational domains providing user-interactive capabilitiesor internal functionality of the software development platform. Thedomains each comprising a process.

A process is being used to refer at a high level to an aspect of thesoftware platform (one or more separate or integrated electronicoperations) directed to a particular aspect or objective of theplatform. As such, the software development platform is configured toimplement a plurality of electronic operational domains providinguser-interactive capabilities or internal functionality of the softwaredevelopment platform. The domains interact and together provide theplatform.

Systems and methods are described for creating software from library andcustom components. In a method for creating software, a server running asoftware creating component may receive input from a customer, where theinput describes at least one aspect of a software program. Based on theinput, the software creating component may determine existing codecomponents that may be used to create the software program, where theexisting code components are stored in a code library accessible by thesoftware creating component. Based on the user input and based on theexisting code components that may be used to create the softwareprogram, the software creating component may determine new codecomponents that must be developed for the software program. And, basedon the existing code components that may be used and based on the newcode components that must be developed, the software creating componentmay provide, to the user, a cost estimate for the software program.

Different embodiments may provide variations on the basic principlesoutlined herein. In an embodiment, the method may further compriseadjusting the cost estimate based on the at least one aspect of thesoftware program. In an embodiment, the at least one aspect of thesoftware program may include at least one of: a platform category, anapplication template, a requirement collection, a platform, a number ofscreens, a feature, a team location, a time to market, and a builddepth. In an embodiment, the build depth may include: a wireframe, adesign, a navigable prototype, a minimal viable product, or a completeproject. In an embodiment, the method may further comprise: sending, bythe software creating program, a set of existing code requirement and aset of new code requirements to a team selector; and generating, by thesoftware creating program, a project template based on the existing codecomponents that may be used and based on the new code components thatmust be developed. In an embodiment, the method may further comprise:generating, by the software creating program, a project schedule basedat least in part on the project template, the project schedule includingevents related to the creation of the software program; and managing, bythe software creating program, the events related to the creation of thesoftware program. In an embodiment, the events related to the creationof the software program may include at least one of: a projectmilestone; a code commit; and a customer message. In an embodiment, themethod may further comprise: passing, by the software creating program,at least one event ID to a communication program; and sending, by thecommunication program, a message to the customer based on the event ID.And in an embodiment, the method may further comprise: receiving, by acommunication program, a message from the customer; and parsing, by thecommunication program, the received message into the software creatingprogram.

As show in FIG. 3B, application 440 include project scoping process 485,pricing process 495, project development process 465, and otherprocesses 425. The project scoping process 485 is configured to providecustomers with the ability to specify the scope of the project. This canbe done by way of user interfaces that permit the user to selecttemplates, features, and/or design characteristics or requirements forthe project. A project scope process can be configured to provide a userwith the ability through interacting with display screens to specify andaccept a scope for the software project.

Pricing process 495 is configured to provide customers with adetermination of the price for the components of the software projectand/or delivery of the software application meeting the specifiedselections by the user as part of the project scoping process. Thepricing process 495 is configured to provide prices for the delivery ofa software application for the software project. The project developmentprocess 465 is configured to provide management and tracking of thesoftware project once initiated. It can involve selecting which softwaredevelopers that are on the platform are assigned portions of theproject. The assignment can be made in the platform by a CPE/CTEselecting developer in the system or can be made automatically. Theproject development process 465 can be configured to selectively assignone or more elements of the software project to developers and manageand track the development process of each software project in theplatform. The discussion herein that encompasses the processfunctionality or is directed to achieving the process objective would beunderstood to be a part of that corresponding process. Other processescan be included in the platform such as instant prototyping.

Graph database 480 is included as part of the application. The graphdatabase stores nodes and edges that represent corresponding entitiesand relationships between entities. Graph database 480 can beimplemented on its own server and a copy of the graph database can be atdiscrete times provided the platform to provide services using the graphdatabase.

The software development platform is configured to collect data fromactivity in the project scope process 485, pricing process 495, andproject development process 465 in accordance with platform-definedgraph data structures. The data is collected is tapped or copied fromthe existing operation of these domains or processes to collecthistorical data about activity in the platform and interactions toaggregate such data. The graph data structures comprising a plurality ofdifferent types of nodes representing entities and the node typescomprising template, feature, and other node types such as developer orproblem and each node type having a set of defined attributes, anddifferent types of edges that represent interrelationship betweenentities.

The platform is configured to generate and store a graph database 480comprising the nodes and edges created from the collected data in theoperation of software development platform and is configured to reuseexisting nodes and edges, add new nodes and edges, and adjust individualattributes assigned to each edge based on new data. For example, a newsoftware project may include a login feature and the login feature waspreviously included in the scope of other previous projects, theplatform does not need to add that node to the graph database since itwas previously used. The edges are defined relationships betweendifferent type of nodes. Attributes can include a count or frequencyassociated with each edge stored in the graph database and represent howmany times that the same edge connection (between the same two nodes)were found in the software projects that have been loaded into the graphdatabase. The graph database manages large scale data in a different waythan generally used databases.

The platform is configured to continue to load software projects (e.g.,sets of features and/or templates into the graph database) and it can ifdesired include nodes or edges for related activities. The softwaredevelopment platform and related information is updated as new softwareprojects are created or initiated in the platform. The softwaredevelopment platform is configured to issue a query to the graphdatabase and in response, receive query results from the graph databaseor from related components that it uses to control one or more parts ofthe operation of the platform (e.g., an action within a process).

The software development platform is configured to implement one or morealgorithms configured to traverse nodes and edges in the graph databasein accordance with one or more criteria of an algorithm. The algorithmcan be selected to correspond to the query, which in this case isdirected to providing feature recommendations. The algorithm cantraverse the knowledge graph to identify different paths starting from anode through its connected edges to other directly connected nodes andsimilarly continue until a criteria of the algorithm is not met (whichcauses that traversal to stop). So, for example, a path may involvenode1-edge1-node2-edge2-node3. The algorithm identifies paths relevantto the query and stops traversing the nodes or edges when the criteriais not met. The algorithm can start with a different node in the graphto apply the algorithm and collect information such as paths can repeatthe procedure over the graph database to discover the graph structure,nodes, edges, and/or paths that meet the criteria. The application ofthe algorithm can be implemented in advance to collect the resultantpath or other information and the results can be stored for handlinglater received queries. The software development platform can beconfigured, in response to the query, to control a user interaction inthe project scoping process comprising displaying an option thatsuggests a feature to include based on the structure of the graphdatabase.

Embodiments of the present invention implement a framework that takesadvantage of the semantic relationships between diverse data points insoftware development platform's database. This is achieved by storingrelated data in a graphical structure. This allows the platform toenhance knowledge around each data-point by leveraging their connectionwith other data-points. FIG. 44 is an illustrative representation of anexample of graph database containing different types of nodes (thecircles) and edges (the lines connecting circles). Six types of nodesare illustrated in FIG. 44 including skill 4402, feature, project, CPE,template, and developer. Each node is for a different such entity so forexample the two developer node be for developers John Smith and JaneBlue. The edges are shown to be directional and they demonstrate forexample developer 4406 has a certain skill 4402. The platform can beconfigured to apply different traversal algorithms to quickly identifyinformation (or set of relevant paths) and potential associations bytraversing the nodes and edges of certain types.

The configured graph database incorporates nodes and entities fromdifferent processes or aspects of the platform which allows forinterrogation and discovery of interrelationship and potentialassociations from paths containing connected nodes and edges across thedifferent tasks, processes, or relevance. The graph database is notsolely focused on the software elements that together form the softwareapplication for a software project but extends into other areas in thesoftware platform and in so doing, provides a greater depth ofperformance. For example, FIG. 45 is an illustration that shows animplementation of nodes involving different aspects of the platform.FIG. 45 illustrates that the defined node types can be template, projectfeature, developer, CPE/CTE, and problem statement. Boxes shown in thediagram contain an illustrative set of attributes for each node type.For a particular project, the collected data that is instantiated in thegraph database can include the range of all of the types of nodes andthe edge connections.

In preferred implementation of embodiments of the present invention,four or five different entities (or nodes), the fifth being creator, areimplemented to configure the software development platform are selectedand used in the graph database process. The entities and correspondingnode types are:

-   -   1. Feature: Features are the atomic unit of a real-world        application that provide functionality to the app. The data        around features is sourced from a content management database        (part of the platform, which can be in features database for        example). which can include features database of FIG. 3B, that        contains preconfigured information such as meta data including        connections or links to other features. A feature is also        defined further herein.    -   2. Projects: A project is a collection of features. These are        used to understand how some features combine to form a real        world application. We source the data of our historical        projects/build cards from a database that stores this historical        information.    -   3. Templates: While projects contain some level of noise in        them, templates are very well structured collection of features        that form a real-world application. Also, the build card        generation process allows a user to base their project/app on a        template, it provides a fair amount of information around the        type of a project. The template data is sourced from a database        that contains the template to feature mappings, which can be in        the features database of FIG. 3B. Template is also further        defined below.    -   4. Problem groups (or Problem): Problem groups are groups of        templates that solve similar types of problems. This gives us an        insight into how features combine towards solving a particular        kind of problems. The data around problem groups is sourced from        the problem-groups table in a platform database (e.g., features        database).    -   5. Creators: Creators or Developers are the key workhorses in a        client project and are assigned to a project based on their        skill and proficiency—(skill level) using the resource        allocation tool (RAT). During the course of the project,        creators are then assigned to several features—stories by the        CPEs, information of which is recorded on a tracker process.

Graph schema that is defined in the platform and applies to the data isused to create and refresh the graph database. For example, the belowtables show an example of graph scheme (the entities/nodes beingexplained above):

A B C D E F 1 Entities Feature Project Template Problem Creators 2Attributes builder_id builder_id builder_id builder_id builder_id 3 namename name statement email 4 bundle_id build_card_id descriptionvendor_name 5 complexity created_date status country 6 interface_typeupdated_date created_date 7 price start_date total_hours 8 time end_datecommunication 9 is_core cost responsiveness 10 descriptionsecurity_deposit delivery_owners hip 11 question timelines skills:expertise score 12 embedding status nb_tracker_logins 13 briefnb_cpe_feedbacks 14 speed rejected_story_ratio 15 squad on_demand_price16 rat_score_v2 17

Graph schema can include relationships between nodes such as:

A B C D 1 Entity 1 Entity 2 Relation Relation Attributes 2 FeatureFeature feature-feature — 3 Project Feature project-feature — 4 TemplateFeature template-feature — 5 Project Template project-template — 6Template Problem template-problem — 7 Creator Project creator-projectcommunication, delivery_ownership, responsiveness, skill_name,skill_expertise, skill_scoreRelations can also have their own set of attributes such as a count foran edge of how many times the same pair of nodes are connected with thatedge.Below are the details for each relation,

-   -   1. Feature—Feature Connections: The existence of an FFC relation        between any two features signifies that those features are        usually linked to each other in a real-world application. This        data is sourced from database that stores “hero-sidekick”        feature mapping data (stores information that includes link that        are commonly or usually linked by human design and/or automatic        determination). The database may also record as part of an        attribute information about how many times the same pair of        nodes are connected.    -   2. Template—Feature/Project—Feature: Templates and projects are        related to features through this relation. This signifies that        the connected feature is a part of that project or template. In        terms of a project it means that the connected feature is a part        of the build card of that project. In terms of templates, the        connected features simply is a part of the feature pool that the        template is made up of    -   3. Project—Template: This relation connects projects to        templates. Any user that lands on a studio interface for        designing the application and starts to ideate their project,        they are presented with an option to base their app on a        pre-existing application template. If the user decides to base        their app on a template, it gets added to their build card. This        relation signifies that a particular project is based on the        connected template.    -   4. Template—Problem: A lot of application templates are a part        of some problem groups. This is based on the industry they        belong to and the problem that they solve. For instance, the        application template of Uber solves a city's transit problem, so        it belongs to that problem group. This relation connects        application templates to the problem groups that define the        problems that the particular template solves.    -   5. Creator—Project: The existence of a creator-project link        signifies that a creator was assigned to a given project.        Moreover, each creator-project edge contains following        attributes which provide a granular view of the allocation:

A B 1 creator-project Description 2 communication sum of CPE feedbackscore for a given project. 3 delivery_ownership sum of CPE feedbackscore for a given project. 4 responsiveness sum of CPE feedback scorefor a given project. 5 skill_name Skill for which creator was assignedto a project - ‘ROR’ etc 6 skill_expertise 7 skill_score

With respect to recommending features, the platform is adapted toprovide the advanced capability using the graph database by beingimplemented in that process with the above four or five nodes andrelations. These are the core or primary pieces that are operated on inthe process. Other nodes or relations may exist in the platform. Inpreferred embodiments, the graph database algorithm and relatedprocesses for feature recommendation is configured to apply operationsor algorithm on this 4/5 nodes and 4/5 (fifth being creator project)relations such as in the below described knowledge graph algorithm andembedding pipeline.

FIG. 46 is an illustrative representation of an implementation of asubsystem 6600 of the platform. It can be a portion of an implementationof the platform in FIG. 3B. Subsystem 6600 can include data ingestion6602 wherein raw data is collected from the internal activity of theplatform (e.g., data taps that collect data for use in the knowledgegraph). Data ingestion uses predefined graph data structures to createnodes from the raw collected data. As shown, the node types areprojects, templates, features, and problems. Other nodes such as creatorcan be included depending on objectives. Data ingestion also usespredefined data structures to create edges or relations from the rawcollected data. As shown, the edges (relations) are project to template,templates to problems, features to projects, and features to template.Additional edges can be included. In knowledge graph stage 6604 theplatform creates or updates the knowledge graph (or graph database)using the nodes and edges created from the collected data during dataingestion 6602. The knowledge graph is copied to the cloud for use bysoftware clients. Clients 6606 are configured to query the knowledgegraph to provide certain functionality. Clients 6606 include a featurerecommendation client that for example, sends a set of features selectedby a customer for a project to the knowledge graph and in response theset of features are applied to the graph database and one or morerecommendation for other features that are found by the knowledge graphis identified and communicated. To clarify, a new project can include atemplate or problem and in turn these include one or more features (thatembody the template or problem). In addition, the traversal algorithmcan include the use of particular node attributes as basis for whetherto traverse or identify paths (or groups of connected nodes and edges).For example, features may have an attribute of advance, intermediate,and beginner. The platform can for example apply an algorithm thattraverses only intermediate features combined with some other attributeto quickly generate relevant information that can for example be used tocontrol the design or operation of the platform.

Now with reference to FIG. 47 , an illustrative diagram is provided thatdemonstrates one type of query, response, and graph database algorithmthat can be applied to provide an improved and advanced softwaredevelopment platform. Plane 7002 is a conceptual representation of thedomain for a node type, which is in this case are features. The nodes inplane 7002 represent different features that are available or have beendeployed in the software development platform to design or scope aproject. Nodes are not the source or object code for that particularfeatures but represent that entity in name and values of the attributesthat are associated with it. If desired, each node can be linked to itscorresponding source code (file) or object code (file). Plane 7002includes nodes f1 7004, f2 7006, and f3 7008. Plane 7010 is a conceptualrepresentation of a customer's build card (one in the process ofdefining project scope, selecting templates or features for theproject). The customer, as shown, has interacted with the softwaredevelopment platform to selectively add features f1 and f2 to the buildcard. The platform, preferably in response, queries the nodes and edgesof the graph database, for example by sending the customer selectednodes to the graph database. The graph database and platform can beadapted to receive and handle this particular of query. The graphdatabase applies a corresponding algorithm, in this case additionalfeature recommendations to generate output from the graph database,which can include related information stored in the database. There caninclude having different algorithms adapted for different situation thatare configured to apply a different operation or analysis on the graphdatabase (e.g., node traversal or identify similar nodes).

In this situation, of FIG. 47 , the platform by applying the algorithmdetermines that customers that chose f1 and f2 often also chose f3. Thisas mentioned can be based on the number of times (an attribute) thoseedges were previously assigned between those nodes (in past project or100 past projects). FIG. 47 illustrates that f1 7004 was selected for abuild card along with f2 7006, f3 7008, and f4, and f2 7006 was oftenselected for a build card with f1 7004 and f3 7008. The diagramillustrates that the graph database using the algorithm would be able todetermine that f3 7008 is “linked” (e.g., pointers, software parameters,logical structure) to the two features in the build card and cangenerate an output identifying f3 as an additional feature (suggestedfeature) for the user to add (or to automatically) add to the build card7010. This may appear simple but in the context of large scale data setand a software development platform involving many features andsignificantly more ingested projects, the determination is complex anddifficult to determine in known software development platformtechnology.

With reference now to the functional block diagram of FIG. 48 , inimplementation the platform can be configured include a server on whichthe graph database resides. The platform can be configured to include amethod that updates, maintains, and delivers the services to platformprocesses. As shown, data is provided in 8002 for incorporation into theknowledge graph where the data is in different planes (categories ortypes of nodes) such as project, feature, template, and problems. Thecontent management system that stores data related to featureconnectivity is provided 8004 within the platform in order to providesuch data. At step (or function) 8006, the provided data from 8002 and8004 are ingested periodically and saved. At 8008, the platform isconfigured with graph scheme and includes methods for adding new nodeand edge types. The platform is configured at 8012 to create or refreshthe knowledge graph instance and save it. The is performed using thegraph schema and ingested data to create or refresh an existing graphdatabase with the new data. The knowledge graph is saved in Object 8014.The platform is configured to use this as the resource for continuing toupdate the knowledge graph without affecting related services thatinteract with the graph database. The platform would want to continue toupdate or refresh the graph database while also providing a live steadyresource for use and interaction in the system. The platform isconfigured to isolate or buffer the ingestion, creation, and refresh ofthe graph database so that for example is running independently on aserver separate from platform operation in providing processes tocustomers, developers or others. The platform is configured to store thediverse large scale data ingested and in accordance with the graphschema in the graph database which contains a wide range of nodes andedges comprising a wide range of software development entities andrelationships on the software development platform. The graph databaseand related or supporting functions or functionality is specificallyadapted for software development platforms and feature recommendationsuch as by having graph schema providing for the node types identifiedherein.

To provide services 8016, a script is used to copy the graph database inits then current form after recent ingestion, creation (or refresh) fromthe graph server, from object 8014. In services 8016, the copied graphdatabase is loaded into the memory for the services and at 80022, theplatform is configured to interact with the loaded graph database toprovide feature recommendations. Once copied it is made “live” for usein the platform. Module 8024 is implemented to allow the services tointeract with the graph database in the production phase of thedatabase.

The nodes and edges can be configured to be directed such that edgespoint in a direction such as from project to features that were includedin that project.

In some embodiments of the present invention, node embedding isimplemented from the graph database. For the purposes of discussion andoperation, the node embedding and related structure or method isconsidered part of the graph database functionality and relatedelements. The platform can rely on node embeddings derived from theknowledge graph. The knowledge graph is likely in practicalimplementation in constant evolution, which means that relevantembeddings are themselves in constant evolution. In addition, eachservice or software client of the platform may rely on a different setupfor the embeddings. For example, one application may require onealgorithm to generate embeddings (e.g., Metapath2vec) while otherapplications will require another algorithm to generate embeddings(e.g., Graph Sage). The operation of these algorithms can be locatedfrom Internet websites.

From a production point of view, platform implements a pipeline thatregularly updates the required embeddings for each application. From adevelopment point of view, the platform is configured to create apackage that allows any relevant developer of a particular applicationto generate embeddings on the fly given a particular setup.

More specifically, from a production perspective the platform isconfigured to be implemented to:

-   -   whenever the knowledge graph is refreshed for an application or        service (application or service in this context referring to the        software in the platform that uses the knowledge graph to        provide one or functions or capabilities), the platform can        determine if the knowledge graph changes also affect the        embeddings required for the application or service (e.g. new        entities added or new edges added);    -   different embedding setups are provided for different        application or services, and when refreshed the right embeddings        are uploaded to the right application or service; and    -   include embedding generation separate from the primary operation        of the platform comprising, for example, project scoping        process, pricing, project management, and testing in order not        to slow the performance of the platform and to avoid the        platform breaking down.

Preferably, the platform is configured to trigger the training of theembedding locally. The package software components and method(s) thatimplement this capability should be very simple to use and preferablyonly requires as input the algorithm name and a hyperparameter. In acurrent embodiment, each application or service in production has aconfiguration file in the form of a Json file: the Json have twoentries, the first entry is the algorithm name (e.g., Metapath2Vec) thesecond entry is itself a json that specifies the hyperparameters of thealgorithms (e.g., metapath_dict, window_size, etc.).

There may also be a readme file in the embedding package specifying thelist of hyper parameter names corresponding to each algorithm name. Oncethe pipeline is triggered the first steps consists in fetching theconfiguration for each application or service to form a masterconfiguration, run embedding generation for each configuration, for eachconfiguration in the master configuration file, preferably first verifythat the required data for the embedding generation changed andpreferably only in this case run the embedding generation and upload theresulting embedding to memory thus replaces the old embedding for thisparticular configuration.

Now with reference to FIG. 49 , an illustrative generation pipeline isprovided as implemented in some embodiments of the present invention,the pipeline is configured to use the graph database to generatedifferent node embeddings that are adapted for different desiredservices, clients, or applications. The pipeline or components thereofcan be implemented in combination with graph database in order toprovide computational simplification, higher relative speed ofinformation retrieval while maintaining accuracy, and adaptability ordynamic ability to be tuned to different needs in the platform andprovide on-demand support due to the pre-generation of the embeddingprior to the need for handling a query or other analytic operation. Theembedding can also be loaded into memory or tables that are not graphdatabases which are easier to store and perform mathematical operationson (e.g., a conversion from graph database to n-dimensional vectors thatare better adapted for computer operations). In operation, the platformis configured to provide feature recommendation in real time in responseto a query for a recommendation comprising selected features. This canbe performed for example using the graph database and embeddingarrangement. Real time refers to instantaneous or immediate response inrelation to the receipt of the query.

Pipeline 900 can include control 9004, representation learning service9006, embedding central repository 9012, and application (productionbranch) 9014. Representation learning service 9006 can includeconfiguration selection component 9008 and embedding generation 9010.Control 9004 comprising one or more control commands that trigger orcontrol the operation of the pipeline or elements thereof.

Configuration selection component 9008 is configured store differentalgorithms used to generate embedding. The algorithm can be specificallyselected for example a corresponding platform service or software clientsuch as feature suggestion. The configuration selection component 9008includes hyper parameters that are parameters that store configurationinformation for the parameters. Each stored hyper parameter is used toconfigure a corresponding algorithm to be adapted to provide the desiredfunctionality. The hyper parameter and algorithm (or link to algorithm)can be stored and fetched from application production branch 9014.

Embedding generation uses the selected algorithm configured inaccordance with the hyper parameters to perform node embedding byapplying the selected (configured) algorithm to the graph database andthe algorithm generates an n-dimensional vector space (n represents thenumber of columns of vector). The n-dimension vector reflects thestructure of the refreshed or created graph database (wherein there iseach node is represented by its corresponding vector) and contains datavalue that are adapted using the corresponding algorithm to identify orcommunicate similarities, explicit relationships, likely relevant edges,similar nodes or similar paths (a path being a series of node and edgesthat form a connected chain that can be traversed without breaks). Thepipeline 9002 can store the different node embedding in centralrepository 9012.

With this approach, the provider of the platform can have its developersbe free to use the information in the knowledge graph in many differentways and free to select and configure an algorithm for the nodegeneration that best suits each new service or software client. Thedeveloper can select the algorithm and its hyper parameters, and canload that into the application production branch 9014 or storageassociated with pipeline 9002. The pipeline can run the different nodeembedding by fetching its configuration file (the algorithm and hyperparameters) and update the node embedding by applying the adapted/tunedalgorithm to the current knowledge graph. The service or software clientcan then retrieve the corresponding nod embedding when the service orsoftware client is executed in the platform. This can provide a robustand highly efficient and quick mechanism for providing the depth ofintelligence in a vast and diverse knowledge graph to many diverse setof services or software clients on the platform dynamically or ondemand. When implemented in combination with system of FIG. 48 , thepipeline is operation on the production copy of the graph database inservices 8016 to provide the node generation as opposed to the graphdatabase stored and maintained separately that is used for refreshing orcreating the graph database. This may cause the graph database topotentially be not as current but it avoids conflicts or interference inoperation if for example the graph database is used simultaneously forboth. It should be understood that in some embodiments, simultaneous useis contemplated.

As such, the software development platform can be configured to includeembedding generation that generates an embedding comprising a pluralityof n-dimensional vectors that in accordance with an embedding algorithmrepresent the graph database, each n-dimensional vector corresponding toa node in the graph database and comprising vector values based onrelationship to other nodes in the graph database. The softwaredevelopment platform can be configured to store a plurality of differenthyper parameters corresponding to different software tools (services,software clients such as feature recommendation) on the platform. Asexplained above, the software development platform can be configured tocontrol the embedding generation with the hyper parameters and generatedifferent embeddings and store the different embeddings corresponding todifferent software tools.

The software development platform can be configured such that a query (aquery seeking information from graph database) is applied to theembedding to generate an output for the control of an operation,display, or recommendation. The software development platform can beconfigured to include a software tool that suggests a feature to add tothe software project based on the embedding. By another example, thesoftware development platform can be configured to include a softwaretool that determines another control or action over the software such asa connection or link being added between two features in the catalogue(in the feature database as part of the predefined characteristics ofthe feature prior to the design process) (and displays screen to showand/or carry out the action) based on the corresponding embedding. Thesoftware development platform can also be configured to control orsuggest a portion of software project to be assigned to a particulardeveloper based on the embedding (values in the n-dimensional vector).

As such an integrated online software development platform integratesamong its many functionality and diverse data machine learning acrossthat is flexible and on-demand for incorporating machine learning toolsthat control the operation of the platform such as to control optionsthat are presented. The architecture can also be implemented to controlthe arrangement and/or connections between features in a softwareproject or other design or development functions using the graphdatabase and/or embedding technology.

With reference now to FIG. 50 , the process involving knowledge graphand embedding is further described. At step 1002, the platform appliesan algorithm to the knowledge graph. The algorithm performs random walksthrough the knowledge graph to generate a corpus. The corpus refers topaths (node-edge-node) sequences in the graph that meet the traversalrequirement of the algorithm. The collection of thoseresulting/identifying paths is the corpus. The algorithm can beconfigured to limit the number of traversals to for example 40 nodes. Atstep 1004, the platform trains parameters of a skip-gram model over thecorpus to generate the embedding. The method of FIG. 50 , preferablyprovides node embedding generation through Metapath2vec, which can befound at Dong, Yuxiao, Nitesh V. Chawla, and Ananthram Swami.“metapath2vec: Scalable representation learning for heterogeneousnetworks.” Proceedings of the 23rd ACM SIGKDD international conferenceon knowledge discovery and data mining. 2017, which is incorporatedherein by reference in its entirety.

With reference now to FIG. 51 , in operation, to receive arecommendation, a list of selected features can be transmitted (as aquery) to the knowledge graph capabilities. At step 1102, the platformretrieves embedding (vector), that has been generated, for each selectedfeature. At step 1104, the platform calculates pairwise dot productsbetween the embedding (vector) of each selected feature and each featurein the feature database of the platform (or depending on situation somesubset thereof or all features). At step 1106, the platform determinesthe score of each feature (not selected features in the catalogue oravailable on the platform). The platform averages the dot product eachfeature in the feature database (obviously not included a selectedfeature) with each selected feature over all of the selected features.For example, if the customer (in a very oversimplified example) selectsf1 and f2 and the catalogue includes f3, f4, and f5. The process (forthe score f3) involves the dot product of f3 and f1 and determining thedot product of f3 and f2, and then adding those to results and dividingby two (to obtain the average). Other implementations are contemplated.At step 1108, the platform determines the feature in the featuredatabase that has the highest scope and selects it to be the featurerecommendation. In some embodiments, the top so many such as two orthree can be selected. In preferred embodiments, as described,collaborative filtering based recommender is implemented using the graphand embedding. Embodiments of the present invention describe particularimplementation details such as graph scheme, algorithm/embedding (fortraversing and determining vectors), and/or node types that areparticularly suited for feature recommendation in the field oftechnology. Other application or tools are not excluded by the discoveryor discoveries.

In some embodiments, the platform may have include a plurality ofdifferent nodes in implementation the recommendation feature, theplatform is configured to operate only certain types of nodes in thegraph database such as project and feature nodes to provide therecommender tool.

FIG. 52 illustrates an exemplary graphical user interface 500 accordingto an embodiment of the present invention. The graphical user interfacemay be displayed in a web browser of a client computing device as partof a web page served by a server. The graphical user interface ofembodiments of the present invention is configured to enable a user toselect from a library of software features 510 to build a softwareapplication.

A feature of the software application is a function or set of functionsfor the application. Conceptually, the feature is the atomic unit of thesoftware project, according to embodiments of the present invention.That is, a feature is an independent unit of predefined functionalitythat comprises the basic building block of the software according toembodiments of the present invention. Accordingly, a feature is thesmallest unit of the desired software application that the customer canemploy (or need conceptualize). Further, if desired, a feature can beemployed in disparate applications with minimal to no change to its corefunctionality, as will be described further down in this specification.This modular nature of the feature enables embodiments of the system ofthe present invention to build a prototype merely by logicallyconnecting a selected set of features.

A feature may include a functionality that can be implemented in amodular fashion and that can be interchangeable between multiplesoftware applications. For example, a feature that requires a user ofsoftware application to login (or a login feature) can be implementedusing the same code and screen or interface across multiple softwareapplications. Other features may require the same core code acrossmultiple applications and platforms but differ in details. For example,an Account Creation feature may differ in details from one applicationto another depending the information that the account creation requiresfrom the user. To that end, the software development platform of thepresent invention enables the user to customize a feature withoutmodifying its core code and functionality and therefore withoutaffecting its interchangeability between software applications.

The library of features 510 may be presented as a set of icons, a list,a drop down menu, or any other means of presenting information ongraphical user interface. Graphical user interface 500 includes featuresets area 502 that displays a list of different feature sets such assecurity or social. In response to a user selecting one of the featuresets, the list of selectable feature that are displayed adjacent to themare updated with the corresponding features in that set. Display area506 displays an icon representation of each selected feature thatcomprises a miniaturized view of this what the corresponding display isrepresented to look like. Area 510 displays a selected one of the iconsfrom 506 such that the user can view a larger view of feature byselecting from the different icons. Option 508 can activate a automatedexpert that assists the user including providing featurerecommendations. A project can be specified and accepted by the user tocontain a set of selected features (e.g., as a result of the selectionof template, the features that defined the template are selected andadded to the build card for the project). The user can interact withinterface 500, for example, after initially selecting a template orproblem in a previous screen to review and evaluate the features in thecurrent build card and add new features from area 510 or remove featuresby interacting with 510 or 506. Interactive display area 506 identifiesthe selected features in the current build card and is configured toscroll laterally to allow the user to peruse the features if the screenis too small to show all of the features. Interface 500 may include abutton or option such as expert option 508 that when selected inresponse display text that as one options displays one or more featurerecommendations for the current project. In response to the user,selecting to add that recommended feature, the selected (recommended)feature an be added to the features to the current build card bedisplayed in interactive display area 506 and if “clicked” by a user,displayed in “zoomed” form in interactive display area (portion ofdisplay screen) 510. Using the interface 500, the user can define all ofthe features that are to be contained in the current project.

A template means a preorganized set of the library of features, whichare available on the system as a way to associate particular templateidea with set of curated features for that template. To clarify, in someinstances the term project template is being used to refer to aframework, build card, or project specification. FIG. 53 illustratesgraphical user interfaces 500 displaying a library of templates 550,according to an embodiment of the present invention. Each template 550of the library provides the basic functional architecture and visuallayout of the software project. In particular, the template 550 providesa predefined and customizable basic process flow process between a setof predefined and customizable features or functions of the softwareapplication. The library of templates 550 may be displayed on thegraphical user interface 500 as a set of icons, a list, a drop downmenu, or any other means of presenting a set of information on agraphical user interface.

In the embodiment illustrated, the templates 550 are grouped by types ofsoftware, such as mobile applications for mobile devices, webapplications for website, marketplace applications that help buyers andsellers transact in real time, e-commerce application, applications forwearable devices such as apple watches or google wear, or any othertypes of applications that may be available on consumer devices. In theembodiment illustrated, the graphical user interface 500 furtherprovides examples of templates within each grouping of templates. Forexample, the mobile application grouping may include a list of mobileapplication templates such as Uber, Snapchat, Quora, Tinder, or otherpopular mobile applications that a customer may want to use as a modelto communicate requirements for their own application. A social mediagrouping for templates may include Facebook, Snapchat, Instagram, andtemplates of other social media applications. It should be noted thatApplicant is not affiliated with the providers of the above applicationsand services whose structures may provide bases for templates in someembodiments.

After the user has selected a template 550, the user is provided withthe opportunity to customize the software project by adding features toor removing features from the template (e.g., FIG. 2 ). In someembodiments, the interface may display a set of pre-selected additionalfeatures specifically corresponding to the template. For example, if thechosen template is that of a social media app, the user may be providedwith additional relevant features such as Private Messages or Take Photo(in FIG. 52 ). Thus, the system enables the user to build software byeither selecting features individually (e.g., “a la carte”) or selectinga predefined set of features or a template, building upon the templateby adding or subtracting features to form the software project.

Referring back to FIG. 3B, in some embodiments, the builder software 440on the server 430 may further comprise process 485 which can comprisefeature selector configured to select a set of features based on inputfrom the user. In such embodiments, the client device 410 may prompt theuser with various questions for specifying the type of softwareapplication and broad set of features desired, rather than presentingthe user with a list of specific features. The feature selector 455 isconfigured to translate the user's input into a set of features to beintegrated to form the target software application.

After the selection of features, or the selection of a template and ifdesired, a set of additional user-selected features for the template onthe graphical user interface, the features are transmitted to the server430 from the client computing device 410. The template would beunderstood as discussed herein to include a set of predeterminedinterconnected features that correspond to a particular model. Asdescribed above, the selection of features may also be generated by afeature selector that receives as input answers to prompts from the userinterface and generates a selection of features therefrom. Uponreceiving the selection of features from the client computing device410, the builder application 440 transmits the set of selected featuresfor example to the knowledge graph and supporting capabilities.

A project, in the context of a node type, means a node created for apast or current project that is saved by a user or customer and as partof the process of the platform includes a set of selected features.

FIG. 54 illustrates an example of a portion of display screen that canbe displayed to the user as part of the projects scope process. Theplatform can display areas that provide selectable problems (discussedabove). The platform can then in response select the correspondingfeatures that correspond to the selected problem. In this option, theplatform can give the user to select/unselect templates within a problembefore deciding to submit it as the user's selection.

FIG. 55 illustrates that platform can be controlled to displayselectable feature recommendations to the current user in the displayscreen in area 1502. In response to interactive with the expertassistance or other element as a button, the platform receives theresults from the query based on the selected features of the user anddisplays one or more selectable features to the user. The displaypermits the user to select the one or more features and in response,adds the recommended features to the user's selected features in thedesign process. If the features are the approved or accepted, those setof features proceed in the platform to the next stage such as togenerate source code.

In the context of graph databases (involving nodes and edges), it isunderstood that an edge is used to characterize direct relation(connection) between two nodes (e.g., directionally).

An algorithm applies to the graph database can for example apply acriterion such as identify all projects that include some or all of theselected features in the build card for the current project. In doingso, the algorithm my ignore or stop traversing paths for a project thatdoes not have any of the selected features.

Each of the system, server, computing device, and computer described inthis application can be implemented on one or more computer systems andbe configured to communicate over a network. In one embodiment, thecomputer system includes a bus or other communication mechanism forcommunicating information, and a hardware processor coupled with bus forprocessing information.

The computer system also includes a main memory, such as a random accessmemory (RAM) or other dynamic storage device, coupled to bus for storinginformation and instructions to be executed by a processor of thecomputer or computing device. Main memory also may be used for storingtemporary variables or other intermediate information during executionof instructions to be executed by a processor. Such instructions, whenstored in non-transitory storage media accessible to processor,configure the computer system into a special-purpose machine that iscustomized to perform the operations specified in the instructions andprovide or be capable of features and functionality described herein.The processes described herein can be implemented as computerinstructions executable by the processor of a computer of computingdevice to performs described process steps the computer instructions canbe saved on nonvolatile or nontransitory memory for providing suchimplementations.

The computer system further includes a read only memory (ROM) or otherstatic storage device coupled to bus for storing static information andinstructions for processor. A storage device, such as a magnetic disk oroptical disk, is provided and coupled to bus for storing information andinstructions.

The computer system may be coupled via bus to a display, such as an LCD,for displaying information to a computer user. An input device,including alphanumeric and other keys, may be coupled to bus forcommunicating information and command selections to processor. Anothertype of user input device is cursor control, such as a mouse, atrackball, touchscreen (e.g., on mobile phones) or cursor direction keysfor communicating direction information and command selections toprocessor and for controlling cursor movement on display. This inputdevice typically has two degrees of freedom in two axes, a first axis(e.g., x) and a second axis (e.g., y), that allows the device to specifypositions in a plane.

The computer system may implement the techniques described herein usingcustomized hard-wired logic, one or more ASICs or FPGAs, firmware and/orprogram logic which in combination with the computer system causes orprograms computer system to provide specialized features. According toone embodiment, the techniques herein are performed by the computersystem in response to the processor executing one or more sequences ofone or more instructions contained in main memory. Such instructions maybe read into main memory from another storage medium, such as storagedevice. Execution of the sequences of instructions contained in mainmemory causes the processor to perform the process steps describedherein. In alternative embodiments, hard-wired circuitry may be used inplace of or in combination with software instructions.

The term storage media as used herein refers to any non-transitory mediathat stores data and/or instructions that cause a machine to operationin a specific fashion. Such storage media may comprise non-volatilemedia and/or volatile media. Non-volatile media includes, for example,optical or magnetic disks, such as storage device. Volatile mediaincludes dynamic memory, such as main memory. Common forms of storagemedia include, for example, a floppy disk, a flexible disk, hard disk,solid state drive, magnetic tape, or any other magnetic data storagemedium, a CD-ROM, any other optical data storage medium, any physicalmedium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM,NVRAM, any other memory chip or cartridge.

Storage media is distinct from but may be used in conjunction withtransmission media. Transmission media participates in transferringinformation between storage media. For example, transmission mediaincludes coaxial cables, copper wire and fiber optics, including thewires that comprise bus. Transmission media can also take the form ofacoustic or light waves, such as those generated during radio-wave andinfra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more instructions to the processor for execution. For example,the instructions may initially be carried on a magnetic disk or solidstate drive of a remote computer. A bus carries the data to main memory,from which processor retrieves and executes the instructions. Theinstructions received by main memory may optionally be stored on storagedevice either before or after execution by the processor.

The computer system also includes a communication interface coupled tobus. The communication interface provides a two-way data communicationcoupling to a network link that is connected to a local network. Forexample, the communication interface may be an integrated servicesdigital network (ISDN) card, cable modem, satellite modem, or a modem toprovide a data communication connection to a corresponding type oftelephone line. As another example, the communication interface may be alocal area network (LAN) card to provide a data communication connectionto a compatible LAN. Wireless links may also be implemented. In any suchimplementation, the communication interface sends and receiveselectrical, electromagnetic or optical signals that carry digital datastreams representing various types of information.

Network link typically provides data communication through one or morenetworks to other data devices. For instance, network link may provide aconnection through local network to a host computer or to data equipmentoperated by an Internet Service Provider (ISP). ISP in turn providesdata communication services through the worldwide packet datacommunication network now commonly referred to as the “Internet.” Localnetwork and Internet both use electrical, electromagnetic or opticalsignals that carry digital data streams. The signals through the variousnetworks and the signals on network link and through the communicationinterface, which carry the digital data to and from the computer system,are example forms of transmission media.

The computer system can send messages and receive data, includingprogram code, through the network(s), network link and the communicationinterface. In the Internet example, a server might transmit a requestedcode for an application program through Internet, ISP, local network andthe communication interface.

The received code may be executed by the processor as it is received,and/or stored in storage device, or other non-volatile storage for laterexecution.

It should be understood that variations, clarifications, ormodifications are contemplated. Applications of the technology to otherfields are also contemplated.

Exemplary systems, devices, components, and methods are described forillustrative purposes. Further, since numerous modifications and changeswill readily be apparent to those having ordinary skill in the art, itis not desired to limit the invention to the exact constructions asdemonstrated in this disclosure. Accordingly, all suitable modificationsand equivalents may be resorted to falling within the scope of theinvention.

Thus, for example, any sequence(s) and/or temporal order of steps ofvarious processes or methods that are described herein are illustrativeand should not be interpreted as being restrictive. Accordingly, itshould be understood that although steps of various processes or methodsor connections or sequence of operations may be shown and described asbeing in a sequence or temporal order, but they are not necessarilylimited to being carried out in any particular sequence or order. Forexample, the steps in such processes or methods generally may be carriedout in various different sequences and orders, while still fallingwithin the scope of the present invention. Moreover, in somediscussions, it would be evident to those of ordinary skill in the artthat a subsequent action, process, or feature is in response to anearlier action, process, or feature.

It is also implicit and understood that the applications or systemsillustratively described herein provide computer-implementedfunctionality that automatically performs a process or process stepsunless the description explicitly describes user intervention or manualoperation.

It is understood from the above description that the functionality andfeatures of the systems, devices, components, or methods of embodimentsof the present invention include generating and sending signals toaccomplish the actions.

It should be understood that claims that include fewer limitations,broader claims, such as claims without requiring a certain feature orprocess step in the appended claim or in the specification,clarifications to the claim elements, different combinations, andalternative implementations based on the specification, or differentuses, are also contemplated by the embodiments of the present invention.

It should be understood that combinations of described features or stepsare contemplated even if they are not described directly together or notin the same context.

The terms or words that are used herein are directed to those ofordinary skill in the art in this field of technology and the meaning ofthose terms or words will be understood from terminology used in thatfield or can be reasonably interpreted based on the plain Englishmeaning of the words in conjunction with knowledge in this field oftechnology. This includes an understanding of implicit features that forexample may involve multiple possibilities, but to a person of ordinaryskill in the art a reasonable or primary understanding or meaning isunderstood.

It should be understood that the above-described examples are merelyillustrative of some of the many specific examples that represent theprinciples described herein. Clearly, those skilled in the art canreadily devise numerous other arrangements without departing from thescope of the present invention.

What is claimed is:
 1. An online software development platform providingan integrated resource for design, development, and purchase ofcustomer-desired software applications for software projects created bycustomers, comprising: One or more computers configured using computerreadable instructions stored in non-transitory computer memory toprovide the software development platform, wherein the softwaredevelopment platform is configured to implement a plurality ofelectronic operational domains providing user-interactive capabilitiesor internal functionalities of the software development platform; thesoftware development platform configured to collect data from activityin the software development platform in accordance with platform-definedgraph data schema, wherein the graph data schema defines a set of nodetypes representing entities, the node types defined to be feature,project, template, problem group, and creator, each node type having aset of defined attributes, and different types of edges that representinterrelationship between entities; wherein a feature node represents anindependent unit of predefined functionality that comprises a basicbuilding block of the platform, a project node represents a collectionof features, template node represents a structured collection offeatures that represent a software application, problem group noderepresents a set of features that solve a problem, and a creator noderepresent a developer; the software development platform is configuredto generate and store a graph database comprising the nodes and edgescreated from the collected data in the operation of software developmentplatform and configured to reuse existing nodes and edges, add new nodesand edges, and adjust individual attributes of existing nodes and edges,wherein the graph database represents via nodes and edges an aggregationof the software projects conducted on the software development platformand related information and is updated to include new software projectsusing collected data; and the software development platform configuredto, in response to a query of the nodes and edges, control one or moreparts of the operation of the platform.
 2. The software developmentplatform of claim 1 wherein the platform is configured to traverse nodesand edges and stop travel to identify one or paths comprising connectednode and edge paths in the graph database in accordance with a graphtraversal algorithm, wherein the platform stops traversal when acriterion of the algorithm is not found.
 3. The software developmentplatform of claim 1 wherein the platform is configured, in response tothe query, to provide a service comprising feature recommendation,timeline, or pricing.
 4. The software development platform of claim 1wherein the graph schema includes defined node attributes comprisingattributes for the feature node comprising complexity and price and forthe project node comprising timelines, status, and developer squad. 5.The software development platform of claim 1 wherein the platform isconfigured to include embedding generation that generates an embeddingcomprising a plurality of n-dimensional vectors that in accordance withan embedding algorithm represent the graph database, each n-dimensionalvector corresponding to a node in the graph database and comprisingvector values based on relationship to other nodes in the graphdatabase.
 6. The software development platform of claim 5 wherein theplatform is configured to store a plurality of different hyperparameters corresponding to different software tools on the platform. 7.The software development platform of claim 1 wherein the platform isconfigured define the graph schema to include edge definitionscomprising feature-feature, project-feature, template-feature,project-template, template-problem, and creator-project.
 8. Anon-transitory computer readable medium storing one or more softwareapplications that causes a computer system to execute a method thatimplements an online software development platform providing anintegrated resource for design and development of customer-desiredsoftware applications, the method comprising: implementing a pluralityof electronic operational domains providing user-interactivecapabilities or internal functionalities of the software developmentplatform; collecting data from activity in the software developmentplatform in accordance with platform-defined graph data schema, whereinthe graph data schema defines a set of node types representing entities,the node types defined to be feature, project, template, problem group,and creator, each node type having a set of defined attributes, anddifferent types of edges that represent interrelationship betweenentities; wherein a feature node represents an independent unit ofpredefined functionality that comprises a basic building block of theplatform, a project node represents a collection of features, templatenode represents a structured collection of features that represent asoftware application, problem group node represents a set of featuresthat solve a problem, and a creator node represent a developer;configuring the platform to generate and store a graph databasecomprising the nodes and edges created from the collected data in theoperation of software development platform and to reuse existing nodesand edges, add new nodes and edges, and adjusting individual attributesof existing nodes and edges, wherein the graph database represents vianodes and edges an aggregation of the software projects conducted on thesoftware development platform and related information and is updated toinclude new software projects using collected data; and in response to aquery of the nodes and edges, controlling one or more parts of theoperation of the platform.
 9. The non-transitory computer readablemedium of claim 8 wherein method comprising configuring the platform totraverse nodes and edges and stop travel to identify one or pathscomprising connected node and edge paths in the graph database inaccordance with a graph traversal algorithm, wherein the platform stopstraversal when a criterion of the algorithm is not found.
 10. Thenon-transitory computer readable medium of claim 8 wherein methodcomprising in response to the query, providing a service comprisingfeature recommendation, timeline, or pricing.
 11. The non-transitorycomputer readable medium of claim 8 wherein the graph schema includesdefined node attributes comprising attributes for the feature nodecomprising complexity and price and for the project node comprisingtimelines, status, and developer squad.
 12. The non-transitory computerreadable medium of claim 8 wherein method comprising embeddinggeneration that generates an embedding comprising a plurality ofn-dimensional vectors that in accordance with an embedding algorithmrepresent the graph database, each n-dimensional vector corresponding toa node in the graph database and comprising vector values based onrelationship to other nodes in the graph database.
 13. Thenon-transitory computer readable medium of claim 8 wherein methodcomprising storing a plurality of different hyper parameterscorresponding to different software tools on the platform.
 14. Thenon-transitory computer readable medium of claim 8 wherein the methodcomprising configuring define the graph schema to include edgedefinitions comprising feature-feature, project-feature,template-feature, project-template, template-problem, andcreator-project.
 15. A computer implemented method for an onlinesoftware development platform providing an integrated resource fordesign and development of customer-desired software applications, themethod comprising: implementing a plurality of electronic operationaldomains providing user-interactive capabilities or internalfunctionalities of the software development platform; collecting datafrom activity in the software development platform in accordance withplatform-defined graph data schema, wherein the graph data schemadefines a set of node types representing entities, the node typesdefined to be feature, project, template, problem group, and creator,each node type having a set of defined attributes, and different typesof edges that represent interrelationship between entities; wherein afeature node represents an independent unit of predefined functionalitythat comprises a basic building block of the platform, a project noderepresents a collection of features, template node represents astructured collection of features that represent a software application,problem group node represents a set of features that solve a problem,and a creator node represent a developer; configuring the platform togenerate and store a graph database comprising the nodes and edgescreated from the collected data in the operation of software developmentplatform and to reuse existing nodes and edges, add new nodes and edges,and adjusting individual attributes of existing nodes and edges, whereinthe graph database represents via nodes and edges an aggregation of thesoftware projects conducted on the software development platform andrelated information and is updated to include new software projectsusing collected data; and in response to a query of the nodes and edges,controlling one or more parts of the operation of the platform.
 16. Thecomputer-implemented method of claim 8 wherein method comprisingconfiguring the platform to traverse nodes and edges and stop travel toidentify one or paths comprising connected node and edge paths in thegraph database in accordance with a graph traversal algorithm, whereinthe platform stops traversal when a criterion of the algorithm is notfound.
 17. The computer-implemented method of claim 8 wherein methodcomprising in response to the query, providing a service comprisingfeature recommendation, timeline, or pricing.
 18. Thecomputer-implemented method of claim 8 wherein the graph schema includesdefined node attributes comprising attributes for the feature nodecomprising complexity and price and for the project node comprisingtimelines, status, and developer squad.
 19. The computer-implementedmethod of claim 8 wherein method comprising embedding generation thatgenerates an embedding comprising a plurality of n-dimensional vectorsthat in accordance with an embedding algorithm represent the graphdatabase, each n-dimensional vector corresponding to a node in the graphdatabase and comprising vector values based on relationship to othernodes in the graph database.
 20. The computer-implemented method ofclaim 8 wherein method comprising storing a plurality of different hyperparameters corresponding to different software tools on the platform.